Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5001b66c8e00af7c1c09991ab2745dc0ef7e02beb30a8bad554a694fe94dfc1e

Tx prefix hash: 615ce14ca6fe6b6eca4128fc3baa62c8ca5e6781eeb7550841b624746e09f23b
Tx public key: b5e9be2f9b9fac00d6eed49889b0ca2d10d71d575a4330dc1f6ef475d990a042
Timestamp: 1703864531 Timestamp [UCT]: 2023-12-29 15:42:11 Age [y:d:h:m:s]: 01:107:02:29:29
Block: 923780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337671 RingCT/type: yes/0
Extra: 01b5e9be2f9b9fac00d6eed49889b0ca2d10d71d575a4330dc1f6ef475d990a04202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db97276fc00a5c3e6e5ba27960b07db01069969415779b81c90f33ee38f7c799 0.600000000000 1381516 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": 923790, "vin": [ { "gen": { "height": 923780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db97276fc00a5c3e6e5ba27960b07db01069969415779b81c90f33ee38f7c799" } } ], "extra": [ 1, 181, 233, 190, 47, 155, 159, 172, 0, 214, 238, 212, 152, 137, 176, 202, 45, 16, 215, 29, 87, 90, 67, 48, 220, 31, 110, 244, 117, 217, 144, 160, 66, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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