Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 725871717119d256ce9d8797a8de5460e918f556e9f8609b80acc0c5c0f83a91

Tx prefix hash: 9e2d54be43448af5e3b3525d13467a2dd9eaf52c38330ae0a14b0d4ea478c42f
Tx public key: e7e921169d9fff70b3c9a975aa340b3c0aea5f484dbf51cb4230220364aae95d
Timestamp: 1754448192 Timestamp [UCT]: 2025-08-06 02:43:12 Age [y:d:h:m:s]: 00:107:12:21:31
Block: 1341188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75832 RingCT/type: yes/0
Extra: 01e7e921169d9fff70b3c9a975aa340b3c0aea5f484dbf51cb4230220364aae95d02110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a9660983220515478d2888f75dd6bbff986fc7d2001cd7bd65ea6b7dc8fda6d 0.600000000000 1829011 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": 1341198, "vin": [ { "gen": { "height": 1341188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a9660983220515478d2888f75dd6bbff986fc7d2001cd7bd65ea6b7dc8fda6d" } } ], "extra": [ 1, 231, 233, 33, 22, 157, 159, 255, 112, 179, 201, 169, 117, 170, 52, 11, 60, 10, 234, 95, 72, 77, 191, 81, 203, 66, 48, 34, 3, 100, 170, 233, 93, 2, 17, 0, 0, 0, 4, 37, 163, 90, 15, 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