Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e32291206efb2722ff886f9e1e01a0f759b6e8c9aa39e437320236088f6a1caa

Tx prefix hash: 386e0c893b3daacc69a5b848b419733c6d9d017a57c62565ec2dd2acc9ebd3a6
Tx public key: 3fcafd0df1e73f76f3f95e18bebee8cba766862bf62fbbb8af1477fd467450ec
Timestamp: 1584759600 Timestamp [UCT]: 2020-03-21 03:00:00 Age [y:d:h:m:s]: 05:020:03:49:44
Block: 85882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1171645 RingCT/type: yes/0
Extra: 013fcafd0df1e73f76f3f95e18bebee8cba766862bf62fbbb8af1477fd467450ec021100000002168ad909000000000000000000

1 output(s) for total of 318.741097743000 dcy

stealth address amount amount idx
00: f801dcc52bebe4723d1e6563b032b2d74e2dc125a4bf0de09ff9a76c45160e8d 318.741097743000 155120 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": 85892, "vin": [ { "gen": { "height": 85882 } } ], "vout": [ { "amount": 318741097743, "target": { "key": "f801dcc52bebe4723d1e6563b032b2d74e2dc125a4bf0de09ff9a76c45160e8d" } } ], "extra": [ 1, 63, 202, 253, 13, 241, 231, 63, 118, 243, 249, 94, 24, 190, 190, 232, 203, 167, 102, 134, 43, 246, 47, 187, 184, 175, 20, 119, 253, 70, 116, 80, 236, 2, 17, 0, 0, 0, 2, 22, 138, 217, 9, 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