Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 631d62bc91fdf9ed1205b31e5b963ff80066444e26a2f750dddbd29b51709646

Tx prefix hash: b30c217a650482b1a724af7c202e9fe88781f37b06386a9322b78b53a42ddf1f
Tx public key: 6a3d5a6cc608afd9ded8748b98b2f5f21ac459c300cbabc9cea79d08e85514e6
Timestamp: 1617050918 Timestamp [UCT]: 2021-03-29 20:48:38 Age [y:d:h:m:s]: 04:027:17:46:20
Block: 229235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1039977 RingCT/type: yes/0
Extra: 016a3d5a6cc608afd9ded8748b98b2f5f21ac459c300cbabc9cea79d08e85514e602110000000f00342baa000000000000000000

1 output(s) for total of 106.770153660000 dcy

stealth address amount amount idx
00: 66b3e9675d76dcaf7c1c2f3572184e35fed6d261809c13f19e46406843b8cb5a 106.770153660000 475613 of 0

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": 229245, "vin": [ { "gen": { "height": 229235 } } ], "vout": [ { "amount": 106770153660, "target": { "key": "66b3e9675d76dcaf7c1c2f3572184e35fed6d261809c13f19e46406843b8cb5a" } } ], "extra": [ 1, 106, 61, 90, 108, 198, 8, 175, 217, 222, 216, 116, 139, 152, 178, 245, 242, 26, 196, 89, 195, 0, 203, 171, 201, 206, 167, 157, 8, 232, 85, 20, 230, 2, 17, 0, 0, 0, 15, 0, 52, 43, 170, 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