Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d045a2c31fb3295dbc7f2948650804b9f7ad7c9480e2e96333fe052d59b736a1

Tx prefix hash: 818c5cdeaddfa69e45468fffa0f828eaf5e13238ef2ae922915da51343062e4e
Tx public key: 3995415419e86e10e3317c53d377c38e32297706bda94e5c180a8fa4c2566669
Timestamp: 1625854728 Timestamp [UCT]: 2021-07-09 18:18:48 Age [y:d:h:m:s]: 03:167:13:41:18
Block: 290977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 890361 RingCT/type: yes/0
Extra: 013995415419e86e10e3317c53d377c38e32297706bda94e5c180a8fa4c25666690211000000223634f08d000000000000000000

1 output(s) for total of 66.661167011000 dcy

stealth address amount amount idx
00: b47eed652dc037081e1b96a2afb8b83b8416172910e7df6d54c8c4e3a139ae21 66.661167011000 609393 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": 290987, "vin": [ { "gen": { "height": 290977 } } ], "vout": [ { "amount": 66661167011, "target": { "key": "b47eed652dc037081e1b96a2afb8b83b8416172910e7df6d54c8c4e3a139ae21" } } ], "extra": [ 1, 57, 149, 65, 84, 25, 232, 110, 16, 227, 49, 124, 83, 211, 119, 195, 142, 50, 41, 119, 6, 189, 169, 78, 92, 24, 10, 143, 164, 194, 86, 102, 105, 2, 17, 0, 0, 0, 34, 54, 52, 240, 141, 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