Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 585b1aa1bb760855fde6d9caeea3f9dad1f618ff68ca99302e7f0c42d4030188

Tx prefix hash: 3cad605853ccd3264ade9610c140c05e5f3fc44fd43e3430defc2cd6f5be9dbc
Tx public key: 2bfe7fd99270ae415769157a7be49915bebb3e43077e6d864108a30550c6db75
Timestamp: 1698552501 Timestamp [UCT]: 2023-10-29 04:08:21 Age [y:d:h:m:s]: 01:346:06:45:31
Block: 879960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506147 RingCT/type: yes/0
Extra: 012bfe7fd99270ae415769157a7be49915bebb3e43077e6d864108a30550c6db75021100000004faf35c9c000000000000000000

1 output(s) for total of 0.745293346000 dcy

stealth address amount amount idx
00: 0a2a27b37e3202de8ea3165e3d321870c8546b26cf2c74a6029bc960f583c1dd 0.745293346000 1335500 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": 879970, "vin": [ { "gen": { "height": 879960 } } ], "vout": [ { "amount": 745293346, "target": { "key": "0a2a27b37e3202de8ea3165e3d321870c8546b26cf2c74a6029bc960f583c1dd" } } ], "extra": [ 1, 43, 254, 127, 217, 146, 112, 174, 65, 87, 105, 21, 122, 123, 228, 153, 21, 190, 187, 62, 67, 7, 126, 109, 134, 65, 8, 163, 5, 80, 198, 219, 117, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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