Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b6aefbc8768194182ff9578961fac1cf651ae332de304fe65f03c0ee01786df

Tx prefix hash: 1a5321a7cf2178db3387d26fdd17759b540e2192eb9918f2b66b6afd2a47d766
Tx public key: 41e905141e69b72e8c528ae26b7c0505c0b4bc45a09f860e7fc8fe7975b26b10
Timestamp: 1675601005 Timestamp [UCT]: 2023-02-05 12:43:25 Age [y:d:h:m:s]: 02:277:01:20:00
Block: 690350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 717344 RingCT/type: yes/0
Extra: 0141e905141e69b72e8c528ae26b7c0505c0b4bc45a09f860e7fc8fe7975b26b10021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.166531404000 dcy

stealth address amount amount idx
00: 869f15bcddd6cc886c5b3ef51f339474a396e39fe874299c8a360219530fe085 3.166531404000 1133072 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": 690360, "vin": [ { "gen": { "height": 690350 } } ], "vout": [ { "amount": 3166531404, "target": { "key": "869f15bcddd6cc886c5b3ef51f339474a396e39fe874299c8a360219530fe085" } } ], "extra": [ 1, 65, 233, 5, 20, 30, 105, 183, 46, 140, 82, 138, 226, 107, 124, 5, 5, 192, 180, 188, 69, 160, 159, 134, 14, 127, 200, 254, 121, 117, 178, 107, 16, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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