Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 229a934eab31c18041f193044da3d61ab8099afadb0d008bba8e814eb6aaa45e

Tx prefix hash: 1b9e0d0691b9c1a1b11783bb4814be52cffbb52229cba6cc5aa58ec99894a985
Tx public key: b0e8fb0482aa1cbbf2f8a1b0b3475ee6e2153b0832e92b679e91e4ed26fe00db
Timestamp: 1702652462 Timestamp [UCT]: 2023-12-15 15:01:02 Age [y:d:h:m:s]: 01:151:23:24:36
Block: 913731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369784 RingCT/type: yes/0
Extra: 01b0e8fb0482aa1cbbf2f8a1b0b3475ee6e2153b0832e92b679e91e4ed26fe00db02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d71252bd4037cc5e17562860d8a6878282d96462ebeb333a44533d204ef7447 0.600000000000 1371007 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": 913741, "vin": [ { "gen": { "height": 913731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d71252bd4037cc5e17562860d8a6878282d96462ebeb333a44533d204ef7447" } } ], "extra": [ 1, 176, 232, 251, 4, 130, 170, 28, 187, 242, 248, 161, 176, 179, 71, 94, 230, 226, 21, 59, 8, 50, 233, 43, 103, 158, 145, 228, 237, 38, 254, 0, 219, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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