Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc4793b28a4507d051838f10142d91a2426b8e2be503bfd75c33a53f33c85b8c

Tx prefix hash: e288d01983099a63dc3c947df001c4c1031cbd8dabb4b0feb5b1097b9901fe8d
Tx public key: 6ee04d3edd6adf7b8ea91c8968c0457ad5bb9667c7fe8ad502cf65cc2d15a46f
Timestamp: 1724906878 Timestamp [UCT]: 2024-08-29 04:47:58 Age [y:d:h:m:s]: 00:220:02:16:18
Block: 1098235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157154 RingCT/type: yes/0
Extra: 016ee04d3edd6adf7b8ea91c8968c0457ad5bb9667c7fe8ad502cf65cc2d15a46f02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0a74e87d65174232310907fe82ce9d8993178109431b66cc8fddb32a474704d 0.600000000000 1573882 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": 1098245, "vin": [ { "gen": { "height": 1098235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0a74e87d65174232310907fe82ce9d8993178109431b66cc8fddb32a474704d" } } ], "extra": [ 1, 110, 224, 77, 62, 221, 106, 223, 123, 142, 169, 28, 137, 104, 192, 69, 122, 213, 187, 150, 103, 199, 254, 138, 213, 2, 207, 101, 204, 45, 21, 164, 111, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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