Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d421b9f122e288a918d39fc0ed4780aeeaca6c549f15ce56c971b8ba1578efad

Tx prefix hash: f5f6f7b0fcd60f79c0b3e399836f3ca26a4ea922cb01a16677ea38d36a5485c0
Tx public key: ed71fee77cc773708690995b5bd2b16f3f204c1491c3f6edfbe243e0af4448c8
Timestamp: 1726259795 Timestamp [UCT]: 2024-09-13 20:36:35 Age [y:d:h:m:s]: 00:243:02:12:07
Block: 1109448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173603 RingCT/type: yes/0
Extra: 01ed71fee77cc773708690995b5bd2b16f3f204c1491c3f6edfbe243e0af4448c8021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de1ba4b2e044ab8638f87821d495fc4ac056cbad22f4909b833264922bb1dd4a 0.600000000000 1587707 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": 1109458, "vin": [ { "gen": { "height": 1109448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de1ba4b2e044ab8638f87821d495fc4ac056cbad22f4909b833264922bb1dd4a" } } ], "extra": [ 1, 237, 113, 254, 231, 124, 199, 115, 112, 134, 144, 153, 91, 91, 210, 177, 111, 63, 32, 76, 20, 145, 195, 246, 237, 251, 226, 67, 224, 175, 68, 72, 200, 2, 17, 0, 0, 0, 5, 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