Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 456a3d31017402ea18113627313788c2fcd6363d2cc81956a7e35c887a30064c

Tx prefix hash: 465f5b551dd2f16aae50b35ca22c6120490222359f215d560d7a0a950281abf9
Tx public key: 6e545d36b4a8bedf34013cc73e2791da8d7a72ad9cc2f6ee06d712d4f8e3bb19
Timestamp: 1706743306 Timestamp [UCT]: 2024-01-31 23:21:46 Age [y:d:h:m:s]: 01:069:04:24:38
Block: 947630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310530 RingCT/type: yes/0
Extra: 016e545d36b4a8bedf34013cc73e2791da8d7a72ad9cc2f6ee06d712d4f8e3bb1902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4803834f84e5d87694d89df72600d5dabe88ed74e4cf47256d6af39ec6ddc3b5 0.600000000000 1405988 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": 947640, "vin": [ { "gen": { "height": 947630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4803834f84e5d87694d89df72600d5dabe88ed74e4cf47256d6af39ec6ddc3b5" } } ], "extra": [ 1, 110, 84, 93, 54, 180, 168, 190, 223, 52, 1, 60, 199, 62, 39, 145, 218, 141, 122, 114, 173, 156, 194, 246, 238, 6, 215, 18, 212, 248, 227, 187, 25, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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