Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4960be811a3e478743d8063d2db06f6b0bf1f658ac6232431a5e52104e2b7a8

Tx prefix hash: 95222c3fa2cd736a397d56ae9ec7badd3067044f776b1af9d983678d42d42ade
Tx public key: 46961349ea6507f0788ae0316db08d97814f16ee6633a6bcbe6fdc2a81a9a86e
Timestamp: 1735360873 Timestamp [UCT]: 2024-12-28 04:41:13 Age [y:d:h:m:s]: 00:170:07:20:58
Block: 1184769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121456 RingCT/type: yes/0
Extra: 0146961349ea6507f0788ae0316db08d97814f16ee6633a6bcbe6fdc2a81a9a86e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0bc441bc37c55f2a7efc0703f3b2df0b07c5af6a68f3af1555df51492def439 0.600000000000 1671228 of 15

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": 1184779, "vin": [ { "gen": { "height": 1184769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0bc441bc37c55f2a7efc0703f3b2df0b07c5af6a68f3af1555df51492def439" } } ], "extra": [ 1, 70, 150, 19, 73, 234, 101, 7, 240, 120, 138, 224, 49, 109, 176, 141, 151, 129, 79, 22, 238, 102, 51, 166, 188, 190, 111, 220, 42, 129, 169, 168, 110, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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