Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dda54545d27b189965a0f5a704876de6e486bb82af1b0346822e1bef9f2a3599

Tx prefix hash: 5e8021dce31109d15f90babe5b92976cb1218e3be967db82e094bd7c51c925ab
Tx public key: cd174c9d84f83ba4efc70d9725818f2b7609b4863ea168405ae04dd1ca52af14
Timestamp: 1649859357 Timestamp [UCT]: 2022-04-13 14:15:57 Age [y:d:h:m:s]: 03:031:19:04:25
Block: 479337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 803313 RingCT/type: yes/0
Extra: 01cd174c9d84f83ba4efc70d9725818f2b7609b4863ea168405ae04dd1ca52af14021100000018a8c141c5000000000000000000

1 output(s) for total of 15.840094658000 dcy

stealth address amount amount idx
00: 777f3bd8f340e3c3d3b212ac402c45a12ae5e119f59231c1ecfbec6785d1a8c2 15.840094658000 900208 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": 479347, "vin": [ { "gen": { "height": 479337 } } ], "vout": [ { "amount": 15840094658, "target": { "key": "777f3bd8f340e3c3d3b212ac402c45a12ae5e119f59231c1ecfbec6785d1a8c2" } } ], "extra": [ 1, 205, 23, 76, 157, 132, 248, 59, 164, 239, 199, 13, 151, 37, 129, 143, 43, 118, 9, 180, 134, 62, 161, 104, 64, 90, 224, 77, 209, 202, 82, 175, 20, 2, 17, 0, 0, 0, 24, 168, 193, 65, 197, 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