Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1a6e1c1690b5ba08892fcac12580c0bbbec1dd765c0c6629e14516f737b676c

Tx prefix hash: 0a2fcd73dcd66c8bf0b632bd05c98ec4688edce313b0887de103fc701360822d
Tx public key: 5aa1afe58d62ca8444f56f9cbfeac1aa11d964e0566a46e6ab9ed5674e4e5bea
Timestamp: 1695477731 Timestamp [UCT]: 2023-09-23 14:02:11 Age [y:d:h:m:s]: 02:045:00:54:54
Block: 854453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551826 RingCT/type: yes/0
Extra: 015aa1afe58d62ca8444f56f9cbfeac1aa11d964e0566a46e6ab9ed5674e4e5bea02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.905404317000 dcy

stealth address amount amount idx
00: 30f8e0ba5c3d7de8e643f76ee38ed761a21d14b0e1d7856cce528a3d73d7adb7 0.905404317000 1308427 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": 854463, "vin": [ { "gen": { "height": 854453 } } ], "vout": [ { "amount": 905404317, "target": { "key": "30f8e0ba5c3d7de8e643f76ee38ed761a21d14b0e1d7856cce528a3d73d7adb7" } } ], "extra": [ 1, 90, 161, 175, 229, 141, 98, 202, 132, 68, 245, 111, 156, 191, 234, 193, 170, 17, 217, 100, 224, 86, 106, 70, 230, 171, 158, 213, 103, 78, 78, 91, 234, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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