Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b414bd3c7b3e67ccfa0b7611031dfa0f416d74a6c117c48dfc0d76ad6bbd7267

Tx prefix hash: 5fd6a20adc15929245f241a507d4efc9910a3737e1675d085da72cd97efe9812
Tx public key: 48e9ef4472b62ce75cfb358512db914fcb08dfdcb55cad713f5b36b0813472f1
Timestamp: 1732982310 Timestamp [UCT]: 2024-11-30 15:58:30 Age [y:d:h:m:s]: 00:123:10:29:21
Block: 1165088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88009 RingCT/type: yes/0
Extra: 0148e9ef4472b62ce75cfb358512db914fcb08dfdcb55cad713f5b36b0813472f102110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5e399c71494e28a08bfd5fde2b6a655abc813d1141f42ba3118fcc549b4195b 0.600000000000 1650763 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": 1165098, "vin": [ { "gen": { "height": 1165088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5e399c71494e28a08bfd5fde2b6a655abc813d1141f42ba3118fcc549b4195b" } } ], "extra": [ 1, 72, 233, 239, 68, 114, 182, 44, 231, 92, 251, 53, 133, 18, 219, 145, 79, 203, 8, 223, 220, 181, 92, 173, 113, 63, 91, 54, 176, 129, 52, 114, 241, 2, 17, 0, 0, 0, 11, 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