Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cf3ffcf647cd016ad647c8dc030ab4bf29a661873d543e1866a3a87a5aed796

Tx prefix hash: 5bb55d02b896fca721e4dc480dbfd63dfad2a564ce7a7798d4685f7411c34685
Tx public key: 08b89bd9119089f15408111ce13378d547a602f4cef28ef9d7661b5191fadd1e
Timestamp: 1584898097 Timestamp [UCT]: 2020-03-22 17:28:17 Age [y:d:h:m:s]: 04:347:18:42:14
Block: 86508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145436 RingCT/type: yes/0
Extra: 0108b89bd9119089f15408111ce13378d547a602f4cef28ef9d7661b5191fadd1e0211000000bc8e8a0ce2000000000000000000

1 output(s) for total of 317.227893661000 dcy

stealth address amount amount idx
00: 3d2cb6a27401542eec89f9e50c30c50efd741fd559f97df335c7ee20e4e31c9b 317.227893661000 156098 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": 86518, "vin": [ { "gen": { "height": 86508 } } ], "vout": [ { "amount": 317227893661, "target": { "key": "3d2cb6a27401542eec89f9e50c30c50efd741fd559f97df335c7ee20e4e31c9b" } } ], "extra": [ 1, 8, 184, 155, 217, 17, 144, 137, 241, 84, 8, 17, 28, 225, 51, 120, 213, 71, 166, 2, 244, 206, 242, 142, 249, 215, 102, 27, 81, 145, 250, 221, 30, 2, 17, 0, 0, 0, 188, 142, 138, 12, 226, 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