Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35ab54805ab998e22997925919332b1133987f5be65c7d236f558a873cb004cd

Tx prefix hash: 72e563f8ce4906960a23e5a2e22a619271a9ecbf6172c3ecdfd5e10e851a58b0
Tx public key: c38d1e14ddcb1517e74390d93f8a41416c892f03ca1532e27dc2a6783c80e152
Timestamp: 1709338479 Timestamp [UCT]: 2024-03-02 00:14:39 Age [y:d:h:m:s]: 01:096:07:23:41
Block: 969176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329880 RingCT/type: yes/0
Extra: 01c38d1e14ddcb1517e74390d93f8a41416c892f03ca1532e27dc2a6783c80e15202110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74d05bd8f5f0708753045447dde72f1297e966f90c2c5b88df52cd0a5b2b3393 0.600000000000 1429005 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": 969186, "vin": [ { "gen": { "height": 969176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74d05bd8f5f0708753045447dde72f1297e966f90c2c5b88df52cd0a5b2b3393" } } ], "extra": [ 1, 195, 141, 30, 20, 221, 203, 21, 23, 231, 67, 144, 217, 63, 138, 65, 65, 108, 137, 47, 3, 202, 21, 50, 226, 125, 194, 166, 120, 60, 128, 225, 82, 2, 17, 0, 0, 0, 12, 82, 212, 126, 148, 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