Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1f656b57858dad0b7a15e61b7097fe136c158e17ec14b7bd006b15e3ddd20ab

Tx prefix hash: 770a30876cdeeafe6e316a8731dd91f4f5eaf585fa03a6b89534e4dd44b90ff1
Tx public key: 52f5a83b4151f9f81ca67e09f466c2100e9954ef225269cafb4abee7b0f2bff6
Timestamp: 1723942968 Timestamp [UCT]: 2024-08-18 01:02:48 Age [y:d:h:m:s]: 00:302:00:46:12
Block: 1090254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215666 RingCT/type: yes/0
Extra: 0152f5a83b4151f9f81ca67e09f466c2100e9954ef225269cafb4abee7b0f2bff602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84715b296b194d5da068372fcfef2d59094a200246a369d5d542a1af54ff78e7 0.600000000000 1564877 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": 1090264, "vin": [ { "gen": { "height": 1090254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84715b296b194d5da068372fcfef2d59094a200246a369d5d542a1af54ff78e7" } } ], "extra": [ 1, 82, 245, 168, 59, 65, 81, 249, 248, 28, 166, 126, 9, 244, 102, 194, 16, 14, 153, 84, 239, 34, 82, 105, 202, 251, 74, 190, 231, 176, 242, 191, 246, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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