Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e472fa85ab80e851577406a62ce395bfa2597d52e8ad1ffcf90b9a40996c90f9

Tx prefix hash: de99dd39d66dbde872f3e11ddf8ab5462d9ae9a69f459e3ad2218c63d2919927
Tx public key: aeb5b55af6f13b78d90573c4f391505b6e88ad9cc93be22db30ccf878d5a3f4c
Timestamp: 1694272309 Timestamp [UCT]: 2023-09-09 15:11:49 Age [y:d:h:m:s]: 01:204:15:33:56
Block: 844438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407365 RingCT/type: yes/0
Extra: 01aeb5b55af6f13b78d90573c4f391505b6e88ad9cc93be22db30ccf878d5a3f4c0211000000044b8f5122000000000000000000

1 output(s) for total of 0.977296690000 dcy

stealth address amount amount idx
00: f30ff6cc7e3a3ad0477b3f56e45446eacfe1349b34a65d54fa4c644fae391f29 0.977296690000 1297746 of 0

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": 844448, "vin": [ { "gen": { "height": 844438 } } ], "vout": [ { "amount": 977296690, "target": { "key": "f30ff6cc7e3a3ad0477b3f56e45446eacfe1349b34a65d54fa4c644fae391f29" } } ], "extra": [ 1, 174, 181, 181, 90, 246, 241, 59, 120, 217, 5, 115, 196, 243, 145, 80, 91, 110, 136, 173, 156, 201, 59, 226, 45, 179, 12, 207, 135, 141, 90, 63, 76, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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