Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04392151aac80ecb641403b8ee3b289be5187fa8e3789e51ec371640ab01fa51

Tx prefix hash: 28040bb91bcc550ec75ea18e511060215de15ea9c37331a0d9c8f674bcbcb113
Tx public key: dea0abd35607d1a9a28c8dc806879f6ccd39ee05bb0f7e9b54a04b97c79fcba6
Timestamp: 1698229058 Timestamp [UCT]: 2023-10-25 10:17:38 Age [y:d:h:m:s]: 01:165:09:51:45
Block: 877279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379207 RingCT/type: yes/0
Extra: 01dea0abd35607d1a9a28c8dc806879f6ccd39ee05bb0f7e9b54a04b97c79fcba6021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.760694916000 dcy

stealth address amount amount idx
00: a456490bd16bafdd214c0b5975e7bc1b164a211fdb801287c98daeab145dce75 0.760694916000 1332649 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": 877289, "vin": [ { "gen": { "height": 877279 } } ], "vout": [ { "amount": 760694916, "target": { "key": "a456490bd16bafdd214c0b5975e7bc1b164a211fdb801287c98daeab145dce75" } } ], "extra": [ 1, 222, 160, 171, 211, 86, 7, 209, 169, 162, 140, 141, 200, 6, 135, 159, 108, 205, 57, 238, 5, 187, 15, 126, 155, 84, 160, 75, 151, 199, 159, 203, 166, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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