Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b32e814d4005722f79f0332b0b40a5b35bd1d453336c05d773f60c18086244aa

Tx prefix hash: d99c654a0783330029beeaa9d11cb77b5c25eca7f5e0a864a98a76ccf24da166
Tx public key: 134e02eb77fa8d58bf17df8aa493edf7ed8a569afcdbef27f6dbd07c5493d69e
Timestamp: 1727900307 Timestamp [UCT]: 2024-10-02 20:18:27 Age [y:d:h:m:s]: 00:163:04:41:29
Block: 1123059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116440 RingCT/type: yes/0
Extra: 01134e02eb77fa8d58bf17df8aa493edf7ed8a569afcdbef27f6dbd07c5493d69e02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d00f526fbb7b0419f8fbe934a1343347910ad2a8e42c62260c162652cbb53280 0.600000000000 1605592 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": 1123069, "vin": [ { "gen": { "height": 1123059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d00f526fbb7b0419f8fbe934a1343347910ad2a8e42c62260c162652cbb53280" } } ], "extra": [ 1, 19, 78, 2, 235, 119, 250, 141, 88, 191, 23, 223, 138, 164, 147, 237, 247, 237, 138, 86, 154, 252, 219, 239, 39, 246, 219, 208, 124, 84, 147, 214, 158, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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