Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f91a760e6a8225b376abafa2a120d0e9352f62fc198a7d08e394fbf054459e91

Tx prefix hash: df6e75f1331e34e352c3d7ae2a34911d106c3a52ede9b3ebfd29199115fb1b71
Tx public key: d89968eff9c422e6c0df5f7922497ece69c3ca9db0691ee0eff8f546761dafeb
Timestamp: 1722092508 Timestamp [UCT]: 2024-07-27 15:01:48 Age [y:d:h:m:s]: 00:244:18:16:51
Block: 1074901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174838 RingCT/type: yes/0
Extra: 01d89968eff9c422e6c0df5f7922497ece69c3ca9db0691ee0eff8f546761dafeb02110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: debc1e1666ae4d3085c83fb1ab8b599d19605a4cff3e583571f2504e01124ca7 0.600000000000 1547420 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1074911, "vin": [ { "gen": { "height": 1074901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "debc1e1666ae4d3085c83fb1ab8b599d19605a4cff3e583571f2504e01124ca7" } } ], "extra": [ 1, 216, 153, 104, 239, 249, 196, 34, 230, 192, 223, 95, 121, 34, 73, 126, 206, 105, 195, 202, 157, 176, 105, 30, 224, 239, 248, 245, 70, 118, 29, 175, 235, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8