Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 838c532397e6d56de8e73d5d9271105a1c2f6e69011e1eb331d086b3218cc210

Tx prefix hash: a9efe6b13e6ca8f4e872ab814d1c075147d387eaa89e864a37f8d95b4adbf699
Tx public key: 5804d37d41c2e7a752432dac8080d471aa5934890583714fe67cdd981ff674f4
Timestamp: 1702134914 Timestamp [UCT]: 2023-12-09 15:15:14 Age [y:d:h:m:s]: 01:099:19:59:04
Block: 909444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332504 RingCT/type: yes/0
Extra: 015804d37d41c2e7a752432dac8080d471aa5934890583714fe67cdd981ff674f4021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45510235fc256ef8d4a8aadbe47417760124dfdc6f02a98cb4dc8ea33f044d93 0.600000000000 1366531 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": 909454, "vin": [ { "gen": { "height": 909444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45510235fc256ef8d4a8aadbe47417760124dfdc6f02a98cb4dc8ea33f044d93" } } ], "extra": [ 1, 88, 4, 211, 125, 65, 194, 231, 167, 82, 67, 45, 172, 128, 128, 212, 113, 170, 89, 52, 137, 5, 131, 113, 79, 230, 124, 221, 152, 31, 246, 116, 244, 2, 17, 0, 0, 0, 3, 230, 210, 127, 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