Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 946197755a139e5a351372389947790b2d4232de991101021ff503157a90cf76

Tx prefix hash: 4248bc4cb1d9dbcaf055849a705986fe823afb35ae7e766e8b23d117feb77fb3
Tx public key: 413b503f3ee3223106073e3bf92b04e07b55d8ecea4760c4927dd273c1dc43bd
Timestamp: 1578818579 Timestamp [UCT]: 2020-01-12 08:42:59 Age [y:d:h:m:s]: 04:299:00:40:05
Block: 43787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1103208 RingCT/type: yes/0
Extra: 01413b503f3ee3223106073e3bf92b04e07b55d8ecea4760c4927dd273c1dc43bd021100000001391a8d0e000000000000000000

1 output(s) for total of 439.456946983000 dcy

stealth address amount amount idx
00: 9e1d75ec89692b6f993f20cb91d96cfa14c4a4cd961d0ce883dd942597341983 439.456946983000 79429 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": 43797, "vin": [ { "gen": { "height": 43787 } } ], "vout": [ { "amount": 439456946983, "target": { "key": "9e1d75ec89692b6f993f20cb91d96cfa14c4a4cd961d0ce883dd942597341983" } } ], "extra": [ 1, 65, 59, 80, 63, 62, 227, 34, 49, 6, 7, 62, 59, 249, 43, 4, 224, 123, 85, 216, 236, 234, 71, 96, 196, 146, 125, 210, 115, 193, 220, 67, 189, 2, 17, 0, 0, 0, 1, 57, 26, 141, 14, 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