Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7551f666b818a92f4c5c7eed5d5644bb841fce711c870376192770ebcaf28196

Tx prefix hash: aa8ad11f00112d41f34c49ffbd9333fc86eba7c9a01f6690701b59f412cef88f
Tx public key: 9199d49362c9c4d269af219882eec3988a79300e891f405d0721deb430f23ead
Timestamp: 1697325343 Timestamp [UCT]: 2023-10-14 23:15:43 Age [y:d:h:m:s]: 01:178:04:28:52
Block: 869775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388384 RingCT/type: yes/0
Extra: 019199d49362c9c4d269af219882eec3988a79300e891f405d0721deb430f23ead02110000000233af99f4000000000000000000

1 output(s) for total of 0.805516409000 dcy

stealth address amount amount idx
00: 7fa50f3f2f0b223bce90b60eac7093443a7a460581b93c079caa11adbc5347e8 0.805516409000 1324630 of 0

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": 869785, "vin": [ { "gen": { "height": 869775 } } ], "vout": [ { "amount": 805516409, "target": { "key": "7fa50f3f2f0b223bce90b60eac7093443a7a460581b93c079caa11adbc5347e8" } } ], "extra": [ 1, 145, 153, 212, 147, 98, 201, 196, 210, 105, 175, 33, 152, 130, 238, 195, 152, 138, 121, 48, 14, 137, 31, 64, 93, 7, 33, 222, 180, 48, 242, 62, 173, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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