Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9eeabea4c1202080b795e5df46194bad9cf6c7c61e8292cd49f8331f210f843

Tx prefix hash: bd4b631128ddcd95548f370a4117bdda7c00e8969c919311c2456ac189b89388
Tx public key: 074e1f1c026542d958357f6f4973625357bed35ebdd3df70a780c624f2a4a2bc
Timestamp: 1646814803 Timestamp [UCT]: 2022-03-09 08:33:23 Age [y:d:h:m:s]: 02:255:19:00:39
Block: 454564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 702285 RingCT/type: yes/0
Extra: 01074e1f1c026542d958357f6f4973625357bed35ebdd3df70a780c624f2a4a2bc021100000001cb8520c2000000000000000000

1 output(s) for total of 19.140374063000 dcy

stealth address amount amount idx
00: 9315d6b8b67a0b15b12a8f033348c08e81d12c52f06e68e9f53720c05c9b4af8 19.140374063000 870233 of 0

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": 454574, "vin": [ { "gen": { "height": 454564 } } ], "vout": [ { "amount": 19140374063, "target": { "key": "9315d6b8b67a0b15b12a8f033348c08e81d12c52f06e68e9f53720c05c9b4af8" } } ], "extra": [ 1, 7, 78, 31, 28, 2, 101, 66, 217, 88, 53, 127, 111, 73, 115, 98, 83, 87, 190, 211, 94, 189, 211, 223, 112, 167, 128, 198, 36, 242, 164, 162, 188, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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