Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 279c9d89600713410dfe831952f6b9acd602bc876e3daf2d7d287cd40ee6c1c6

Tx prefix hash: 2ad07e88b2f768e36265eae86c141ad0d559b2ab1434b84c9865ebf457fa5d8a
Tx public key: 03d338322f6ff8afb50032f0e9b6cbfdf219b3c36af1265f82fbd63d9affbac9
Timestamp: 1623023796 Timestamp [UCT]: 2021-06-06 23:56:36 Age [y:d:h:m:s]: 03:172:22:32:09
Block: 273535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 888164 RingCT/type: yes/0
Extra: 0103d338322f6ff8afb50032f0e9b6cbfdf219b3c36af1265f82fbd63d9affbac90211000000039c1fbdcc000000000000000000

1 output(s) for total of 76.168911376000 dcy

stealth address amount amount idx
00: 0bdc1cf452ae6d7a27599ea9e66e021e1261bf6c8db6bc85775ff13499cafd11 76.168911376000 573884 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": 273545, "vin": [ { "gen": { "height": 273535 } } ], "vout": [ { "amount": 76168911376, "target": { "key": "0bdc1cf452ae6d7a27599ea9e66e021e1261bf6c8db6bc85775ff13499cafd11" } } ], "extra": [ 1, 3, 211, 56, 50, 47, 111, 248, 175, 181, 0, 50, 240, 233, 182, 203, 253, 242, 25, 179, 195, 106, 241, 38, 95, 130, 251, 214, 61, 154, 255, 186, 201, 2, 17, 0, 0, 0, 3, 156, 31, 189, 204, 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