Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bea8021e5224aadd4bcac4ad0138886da1019d4c4e33339c2cb12d9382530fe5

Tx prefix hash: ea8fdb3a2667213473114b5e06823ccbfa07999fa7348759ddc6101f748b3964
Tx public key: 282c948fab3f178cba1a62c2fccef5f5e0bef962defe8a08711bf02b923bb443
Timestamp: 1696915085 Timestamp [UCT]: 2023-10-10 05:18:05 Age [y:d:h:m:s]: 02:026:00:32:11
Block: 866377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538208 RingCT/type: yes/0
Extra: 01282c948fab3f178cba1a62c2fccef5f5e0bef962defe8a08711bf02b923bb443021100000006faf35c9c000000000000000000

1 output(s) for total of 0.826682292000 dcy

stealth address amount amount idx
00: 352523c794d4e7da233e97a660e8acf188f04df15e830109f530672fd610963e 0.826682292000 1320965 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": 866387, "vin": [ { "gen": { "height": 866377 } } ], "vout": [ { "amount": 826682292, "target": { "key": "352523c794d4e7da233e97a660e8acf188f04df15e830109f530672fd610963e" } } ], "extra": [ 1, 40, 44, 148, 143, 171, 63, 23, 140, 186, 26, 98, 194, 252, 206, 245, 245, 224, 190, 249, 98, 222, 254, 138, 8, 113, 27, 240, 43, 146, 59, 180, 67, 2, 17, 0, 0, 0, 6, 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