Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68bbb813c58e45465db8cc493b1a78ee56a51d080c69e18eacff4108927ee1fe

Tx prefix hash: b4031ecf021a98277fd2d5a9a4c689e55b21ed7d1344e96843a39e74a1300ff8
Tx public key: 5a8d228df49a58e5f1a544905d7aa9993ed1f5c2098329455062da9efe2b99f4
Timestamp: 1581559150 Timestamp [UCT]: 2020-02-13 01:59:10 Age [y:d:h:m:s]: 04:362:05:59:22
Block: 63781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150871 RingCT/type: yes/0
Extra: 015a8d228df49a58e5f1a544905d7aa9993ed1f5c2098329455062da9efe2b99f40211000000034ac5aa02000000000000000000

1 output(s) for total of 377.283561439000 dcy

stealth address amount amount idx
00: 2aa0e74fea9c0c23277af8210dbf45811997c41a8bdcea1f88ca3782fd98c0f8 377.283561439000 117585 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": 63791, "vin": [ { "gen": { "height": 63781 } } ], "vout": [ { "amount": 377283561439, "target": { "key": "2aa0e74fea9c0c23277af8210dbf45811997c41a8bdcea1f88ca3782fd98c0f8" } } ], "extra": [ 1, 90, 141, 34, 141, 244, 154, 88, 229, 241, 165, 68, 144, 93, 122, 169, 153, 62, 209, 245, 194, 9, 131, 41, 69, 80, 98, 218, 158, 254, 43, 153, 244, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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