Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c53b5dcdefb2169ff46a5466fdabce90f1b8834abdb4dbd305089b8526b0d7c6

Tx prefix hash: 5408b543437c3a0e6e7c7d5d3a3ec0146b5d12230523cb83f3544640517009e2
Tx public key: 055368dc0b4570a9f8c02606a8f67177dac23d0911a496fab4f9fa2480933a28
Timestamp: 1730837338 Timestamp [UCT]: 2024-11-05 20:08:58 Age [y:d:h:m:s]: 00:152:13:24:30
Block: 1147315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108861 RingCT/type: yes/0
Extra: 01055368dc0b4570a9f8c02606a8f67177dac23d0911a496fab4f9fa2480933a28021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2114dc88a1a275d53d97e56232cb5f95341fd41add3017a8b34908defcbe79c1 0.600000000000 1632010 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": 1147325, "vin": [ { "gen": { "height": 1147315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2114dc88a1a275d53d97e56232cb5f95341fd41add3017a8b34908defcbe79c1" } } ], "extra": [ 1, 5, 83, 104, 220, 11, 69, 112, 169, 248, 192, 38, 6, 168, 246, 113, 119, 218, 194, 61, 9, 17, 164, 150, 250, 180, 249, 250, 36, 128, 147, 58, 40, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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