Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e73c6969a17ece473c9e0c999f40923e8039b6feb8d8a46663f169b4ae19bb47

Tx prefix hash: fdfcbb19e73d732967bed176da51cb7ade5c9342d4de6909a6bec3f5854475d4
Tx public key: e248f7278337d762dced6d0e75ab4b5558ba6ef8dd9775ba09ca7d6b71f36ce5
Timestamp: 1711619970 Timestamp [UCT]: 2024-03-28 09:59:30 Age [y:d:h:m:s]: 01:044:19:49:29
Block: 988091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293013 RingCT/type: yes/0
Extra: 01e248f7278337d762dced6d0e75ab4b5558ba6ef8dd9775ba09ca7d6b71f36ce50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb7e1134895cac3b903b70ebfe77c13d50fc3a1fd7e7d707cd9841aa4dce6912 0.600000000000 1448352 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": 988101, "vin": [ { "gen": { "height": 988091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb7e1134895cac3b903b70ebfe77c13d50fc3a1fd7e7d707cd9841aa4dce6912" } } ], "extra": [ 1, 226, 72, 247, 39, 131, 55, 215, 98, 220, 237, 109, 14, 117, 171, 75, 85, 88, 186, 110, 248, 221, 151, 117, 186, 9, 202, 125, 107, 113, 243, 108, 229, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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