Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1045bcb919202ffb260e385554b0cedf08c2f583d7efa57e3547924ed52ac671

Tx prefix hash: 62a0e65c5dca5a52307b310ce38c2ce27b71465905d53590ebcde66c958ef643
Tx public key: d290f2268d13c323a911dc186c34c74f6a8ec465f7931e1fc2174f62f321cfb8
Timestamp: 1731323861 Timestamp [UCT]: 2024-11-11 11:17:41 Age [y:d:h:m:s]: 00:216:07:43:57
Block: 1151345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154387 RingCT/type: yes/0
Extra: 01d290f2268d13c323a911dc186c34c74f6a8ec465f7931e1fc2174f62f321cfb8021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bca1f5c72b8a7494dce0cd44bbfd62f85bb8cd78bbd9426b624a1fc0a2c8da63 0.600000000000 1636858 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": 1151355, "vin": [ { "gen": { "height": 1151345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bca1f5c72b8a7494dce0cd44bbfd62f85bb8cd78bbd9426b624a1fc0a2c8da63" } } ], "extra": [ 1, 210, 144, 242, 38, 141, 19, 195, 35, 169, 17, 220, 24, 108, 52, 199, 79, 106, 142, 196, 101, 247, 147, 30, 31, 194, 23, 79, 98, 243, 33, 207, 184, 2, 17, 0, 0, 0, 6, 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