Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 039a7878105022cd9da183de65d3661f28dd6ca8d8b4d40a8484d86237180366

Tx prefix hash: 5d88ef8687d6293c3bf305feec5260fd0d76ad0d04f168ea4ac07728eb9e52ba
Tx public key: 50030d1b2ffea0735f757283a9dca7ccd491c9d40a85bbd6cfa46c202155c652
Timestamp: 1702562926 Timestamp [UCT]: 2023-12-14 14:08:46 Age [y:d:h:m:s]: 01:333:10:29:37
Block: 912993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497170 RingCT/type: yes/0
Extra: 0150030d1b2ffea0735f757283a9dca7ccd491c9d40a85bbd6cfa46c202155c652021100000007faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecb3cc6cb9a2c6b504f7d6b4a5dc2c3ffa7803eb4709acbbd36b90f7fc65ad47 0.600000000000 1370233 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": 913003, "vin": [ { "gen": { "height": 912993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecb3cc6cb9a2c6b504f7d6b4a5dc2c3ffa7803eb4709acbbd36b90f7fc65ad47" } } ], "extra": [ 1, 80, 3, 13, 27, 47, 254, 160, 115, 95, 117, 114, 131, 169, 220, 167, 204, 212, 145, 201, 212, 10, 133, 187, 214, 207, 164, 108, 32, 33, 85, 198, 82, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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