Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e915cba864eb9069c3f12b3b9436ef92fbff5ab6629ee4502ae84f5b973f7aae

Tx prefix hash: 726e632d86c4d8bd306ff39cfe357bffe9119884ed160a673471d1a5bff17d1f
Tx public key: 605e3e9e04062be16d30dcbcbfcd59496ae9d42c8d0b3d3e16d6d5620a026247
Timestamp: 1703890060 Timestamp [UCT]: 2023-12-29 22:47:40 Age [y:d:h:m:s]: 01:134:04:54:17
Block: 923990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357051 RingCT/type: yes/0
Extra: 01605e3e9e04062be16d30dcbcbfcd59496ae9d42c8d0b3d3e16d6d5620a026247021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90e62c6ca9a4edb3a2ff6c71465b3c4a65fa997fa0a93ca2b9a16964cfaa9d3e 0.600000000000 1381732 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": 924000, "vin": [ { "gen": { "height": 923990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90e62c6ca9a4edb3a2ff6c71465b3c4a65fa997fa0a93ca2b9a16964cfaa9d3e" } } ], "extra": [ 1, 96, 94, 62, 158, 4, 6, 43, 225, 109, 48, 220, 188, 191, 205, 89, 73, 106, 233, 212, 44, 141, 11, 61, 62, 22, 214, 213, 98, 10, 2, 98, 71, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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