Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4e61b8bcfdb669a3292705071c6119a4330cb2ccdc204ced68970d132bfa88e

Tx prefix hash: 8a5f3d61c226570bfa9b83dbf981c839c0e28f10f7037179254255b0f6aac272
Tx public key: 5cb2686913ee7719d536a1106650a720967be997c06d7e7b924bee491ebf421f
Timestamp: 1632114689 Timestamp [UCT]: 2021-09-20 05:11:29 Age [y:d:h:m:s]: 03:219:09:42:29
Block: 337339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 932604 RingCT/type: yes/0
Extra: 015cb2686913ee7719d536a1106650a720967be997c06d7e7b924bee491ebf421f02110000002d5d7cc334000000000000000000

1 output(s) for total of 46.801125026000 dcy

stealth address amount amount idx
00: ab6b00e1d6890f2d44dc1a7ca337e1afbcca7be0917e2866cf0975b8b700c9c9 46.801125026000 694662 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": 337349, "vin": [ { "gen": { "height": 337339 } } ], "vout": [ { "amount": 46801125026, "target": { "key": "ab6b00e1d6890f2d44dc1a7ca337e1afbcca7be0917e2866cf0975b8b700c9c9" } } ], "extra": [ 1, 92, 178, 104, 105, 19, 238, 119, 25, 213, 54, 161, 16, 102, 80, 167, 32, 150, 123, 233, 151, 192, 109, 126, 123, 146, 75, 238, 73, 30, 191, 66, 31, 2, 17, 0, 0, 0, 45, 93, 124, 195, 52, 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