Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbc1764ed0dcde2e6b78bcc81c31c7ec3bf2b27c5e56aabe3a4073fd6472794e

Tx prefix hash: 887d859fd17b7f4c4f5c496e34441c41201eaf9254d457a94bf91cdd888c9436
Tx public key: 8a47ed8bbfa48af4d1ccc6101971c96918c45486d1db4ee882f40c86d69df8f3
Timestamp: 1732710809 Timestamp [UCT]: 2024-11-27 12:33:29 Age [y:d:h:m:s]: 01:062:04:13:34
Block: 1162833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302759 RingCT/type: yes/0
Extra: 018a47ed8bbfa48af4d1ccc6101971c96918c45486d1db4ee882f40c86d69df8f3021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aad4ab1720461e410e8d5a2273dd93151cf03ef6cb0acde5d3c1887dd4f84100 0.600000000000 1648496 of 15

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": 1162843, "vin": [ { "gen": { "height": 1162833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aad4ab1720461e410e8d5a2273dd93151cf03ef6cb0acde5d3c1887dd4f84100" } } ], "extra": [ 1, 138, 71, 237, 139, 191, 164, 138, 244, 209, 204, 198, 16, 25, 113, 201, 105, 24, 196, 84, 134, 209, 219, 78, 232, 130, 244, 12, 134, 214, 157, 248, 243, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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