Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1f69bd95ea9c87ef0a6fba418000469c0181f019bf0ea55e5a38761087e5999

Tx prefix hash: 6d825ec16eafebfac1c1860826e57adc9fdc883b5006405af4e31c2e7a92d249
Tx public key: 0ea73f00511b1ca488725bf450b977c8ed6a6295f706c3033e3cfa712ec1094f
Timestamp: 1715406258 Timestamp [UCT]: 2024-05-11 05:44:18 Age [y:d:h:m:s]: 00:262:18:19:05
Block: 1019501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187771 RingCT/type: yes/0
Extra: 010ea73f00511b1ca488725bf450b977c8ed6a6295f706c3033e3cfa712ec1094f021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41bdc15d69e24bc527f998e35d88effef4a4d1a40c8885c9204d5bfe887e6520 0.600000000000 1483482 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": 1019511, "vin": [ { "gen": { "height": 1019501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41bdc15d69e24bc527f998e35d88effef4a4d1a40c8885c9204d5bfe887e6520" } } ], "extra": [ 1, 14, 167, 63, 0, 81, 27, 28, 164, 136, 114, 91, 244, 80, 185, 119, 200, 237, 106, 98, 149, 247, 6, 195, 3, 62, 60, 250, 113, 46, 193, 9, 79, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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