Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c36d13304eeeb37d5f35017ecb244341ffad6e28e0c2abc4a154fc7956768968

Tx prefix hash: 71f23254214f486fbb9a1202bfb3e50c4ec565b7a780d2b2286259d2a101a86f
Tx public key: 1c47453fb4afe376a0a103f5311f62c32245d2c6505dc026a26da46b72b67179
Timestamp: 1704406781 Timestamp [UCT]: 2024-01-04 22:19:41 Age [y:d:h:m:s]: 01:311:06:51:55
Block: 928257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481311 RingCT/type: yes/0
Extra: 011c47453fb4afe376a0a103f5311f62c32245d2c6505dc026a26da46b72b6717902110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cbf34ede60c8d4c4ad8cf602f4d06b33833a06efedf0ea5a069db53f2db7548 0.600000000000 1386115 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": 928267, "vin": [ { "gen": { "height": 928257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cbf34ede60c8d4c4ad8cf602f4d06b33833a06efedf0ea5a069db53f2db7548" } } ], "extra": [ 1, 28, 71, 69, 63, 180, 175, 227, 118, 160, 161, 3, 245, 49, 31, 98, 195, 34, 69, 210, 198, 80, 93, 192, 38, 162, 109, 164, 107, 114, 182, 113, 121, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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