Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 384467be38641857cecc93f109f47651c48c9783cd308ecd8e0769f5f29253c0

Tx prefix hash: e5394f7320dd746bac40def8192ad02ee4e59863c4752f57a4cd6b8ddcb7f40f
Tx public key: d4e04f4d4620ddd9ea43f2c37d6acb9e6aa636a7fb8938fa2312914ae7b4da34
Timestamp: 1583750076 Timestamp [UCT]: 2020-03-09 10:34:36 Age [y:d:h:m:s]: 05:086:11:34:39
Block: 79028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1217593 RingCT/type: yes/0
Extra: 01d4e04f4d4620ddd9ea43f2c37d6acb9e6aa636a7fb8938fa2312914ae7b4da340211000000256d997e00000000000000000000

1 output(s) for total of 335.852218403000 dcy

stealth address amount amount idx
00: 64c80cb1ca1a5aa34c7cad783f290cb0e0f3eae60205efa91c8d478564abc50e 335.852218403000 144756 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": 79038, "vin": [ { "gen": { "height": 79028 } } ], "vout": [ { "amount": 335852218403, "target": { "key": "64c80cb1ca1a5aa34c7cad783f290cb0e0f3eae60205efa91c8d478564abc50e" } } ], "extra": [ 1, 212, 224, 79, 77, 70, 32, 221, 217, 234, 67, 242, 195, 125, 106, 203, 158, 106, 166, 54, 167, 251, 137, 56, 250, 35, 18, 145, 74, 231, 180, 218, 52, 2, 17, 0, 0, 0, 37, 109, 153, 126, 0, 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