Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1baed35e18cdd4ba72b2ed1aef86efd06f451d5ebc56b9f74941a3544aa1d4

Tx prefix hash: c5e800f34d81a3e9202cab3dd67f56a81d6c75acbbdedd22c9ae548900dbd371
Tx public key: f364dc76cf0e81d4f7869f1b67c2f1df33d7c5f5a654a26f769b4309d980dfc7
Timestamp: 1713620231 Timestamp [UCT]: 2024-04-20 13:37:11 Age [y:d:h:m:s]: 00:358:19:34:45
Block: 1004648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256536 RingCT/type: yes/0
Extra: 01f364dc76cf0e81d4f7869f1b67c2f1df33d7c5f5a654a26f769b4309d980dfc70211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b8da8ae7e4f4bd0b0d2abb9002e09ab5189cedf1a61a0ac10ecf716b8f44fda 0.600000000000 1465218 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": 1004658, "vin": [ { "gen": { "height": 1004648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b8da8ae7e4f4bd0b0d2abb9002e09ab5189cedf1a61a0ac10ecf716b8f44fda" } } ], "extra": [ 1, 243, 100, 220, 118, 207, 14, 129, 212, 247, 134, 159, 27, 103, 194, 241, 223, 51, 215, 197, 245, 166, 84, 162, 111, 118, 155, 67, 9, 217, 128, 223, 199, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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