Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50f87d882395bc618e1e414548ab616157caa3ae5dc764b995374ff8c45c97b6

Tx prefix hash: 9cf2680e4ab32b036a3d8bbe761b1d5c1f82d853fd2c9423cce1e40242a0161c
Tx public key: d19cb4557257681c3ec6d721e5788dad278bf80dab429f483b06d08a5db7c555
Timestamp: 1686483841 Timestamp [UCT]: 2023-06-11 11:44:01 Age [y:d:h:m:s]: 01:209:15:54:55
Block: 779949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411239 RingCT/type: yes/0
Extra: 01d19cb4557257681c3ec6d721e5788dad278bf80dab429f483b06d08a5db7c555021100000005272bcc39000000000000000000

1 output(s) for total of 1.598473166000 dcy

stealth address amount amount idx
00: 0ca3e4217bceec3c8f54991c5e99eb3218cd99407c219902f5073c5482c59a92 1.598473166000 1229638 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": 779959, "vin": [ { "gen": { "height": 779949 } } ], "vout": [ { "amount": 1598473166, "target": { "key": "0ca3e4217bceec3c8f54991c5e99eb3218cd99407c219902f5073c5482c59a92" } } ], "extra": [ 1, 209, 156, 180, 85, 114, 87, 104, 28, 62, 198, 215, 33, 229, 120, 141, 173, 39, 139, 248, 13, 171, 66, 159, 72, 59, 6, 208, 138, 93, 183, 197, 85, 2, 17, 0, 0, 0, 5, 39, 43, 204, 57, 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