Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f46cc36e34da2cea6800b336717579011834b51c6a87acf70856ec752bcc744f

Tx prefix hash: 9e6d6cf3908b8f0d1622150b9737c0dcfeb4a0adb5f15395d03a075be1f420c7
Tx public key: 1a1cde43d554ea0fe45c5aeb36dccfc55687881c3bbf90a5f328e0a0efc320ac
Timestamp: 1719469528 Timestamp [UCT]: 2024-06-27 06:25:28 Age [y:d:h:m:s]: 01:136:20:02:56
Block: 1053146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356355 RingCT/type: yes/0
Extra: 011a1cde43d554ea0fe45c5aeb36dccfc55687881c3bbf90a5f328e0a0efc320ac02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37db5daf17ada0b8ac4342cbd6c778608c7bc0fdf797e9ced7c047d65022d6f1 0.600000000000 1523493 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": 1053156, "vin": [ { "gen": { "height": 1053146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37db5daf17ada0b8ac4342cbd6c778608c7bc0fdf797e9ced7c047d65022d6f1" } } ], "extra": [ 1, 26, 28, 222, 67, 213, 84, 234, 15, 228, 92, 90, 235, 54, 220, 207, 197, 86, 135, 136, 28, 59, 191, 144, 165, 243, 40, 224, 160, 239, 195, 32, 172, 2, 17, 0, 0, 0, 3, 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