Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05a039f2b05b675778e9ccbaf6dee7c5e2dba235ab1491727d4400bee3f84525

Tx prefix hash: 487e4baa1188eb7eddc45a48470d1b4b7dc8f09cf868444319976e0c28794e6a
Tx public key: f8921efbf6cfac7f89296c610416cfe65a280531e4e40c641cbba8f666e43045
Timestamp: 1725154269 Timestamp [UCT]: 2024-09-01 01:31:09 Age [y:d:h:m:s]: 00:220:20:02:23
Block: 1100284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157681 RingCT/type: yes/0
Extra: 01f8921efbf6cfac7f89296c610416cfe65a280531e4e40c641cbba8f666e43045021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56dfd296242c2e6b67d2e95a0f3610b00fb3344846c2acf2a5ce1ea42ffc48b9 0.600000000000 1576259 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": 1100294, "vin": [ { "gen": { "height": 1100284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56dfd296242c2e6b67d2e95a0f3610b00fb3344846c2acf2a5ce1ea42ffc48b9" } } ], "extra": [ 1, 248, 146, 30, 251, 246, 207, 172, 127, 137, 41, 108, 97, 4, 22, 207, 230, 90, 40, 5, 49, 228, 228, 12, 100, 28, 187, 168, 246, 102, 228, 48, 69, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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