Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f82433a5b0f2376fc14e02f80f1da82c00da3272f0fc3ad9157cc64457cd71f5

Tx prefix hash: 996da22fa69cd9ef1a00d5b54e3eb654f6fca43c9d63d1ba21229df436f12c0f
Tx public key: 54d6566223de5fe5a40544267133d5df6aaf6a4203299a95ff95d690c93541cd
Timestamp: 1660357275 Timestamp [UCT]: 2022-08-13 02:21:15 Age [y:d:h:m:s]: 02:243:23:46:36
Block: 564637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 695610 RingCT/type: yes/0
Extra: 0154d6566223de5fe5a40544267133d5df6aaf6a4203299a95ff95d690c93541cd021100000001faf35c9c000000000000000000

1 output(s) for total of 8.262725743000 dcy

stealth address amount amount idx
00: 215e728e03330c55a71d517f471338a0c63bd7f2fdcf5a43688ed3a5c4d7a125 8.262725743000 997489 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": 564647, "vin": [ { "gen": { "height": 564637 } } ], "vout": [ { "amount": 8262725743, "target": { "key": "215e728e03330c55a71d517f471338a0c63bd7f2fdcf5a43688ed3a5c4d7a125" } } ], "extra": [ 1, 84, 214, 86, 98, 35, 222, 95, 229, 164, 5, 68, 38, 113, 51, 213, 223, 106, 175, 106, 66, 3, 41, 154, 149, 255, 149, 214, 144, 201, 53, 65, 205, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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