Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b7f78982258a903d0a0a204515de06a824c5af20f5b599feaad4e185ac90859

Tx prefix hash: 7fd680f6bb35c6e3ebc8cc4d3b31cca1dedb458c8f75d778e60a1d791ca5ad0a
Tx public key: 3bb5404427058c9a0dbbb045a850fb2a2421147abf428159bda142f8a60fa2d5
Timestamp: 1675577736 Timestamp [UCT]: 2023-02-05 06:15:36 Age [y:d:h:m:s]: 02:098:06:25:37
Block: 690149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591874 RingCT/type: yes/0
Extra: 013bb5404427058c9a0dbbb045a850fb2a2421147abf428159bda142f8a60fa2d50211000000035029cbac000000000000000000

1 output(s) for total of 3.171571050000 dcy

stealth address amount amount idx
00: 6e2b91abd28ee0a13435c4746c62bbb2fe0254ff22bef42b42b92e0f0c1e41d3 3.171571050000 1132857 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": 690159, "vin": [ { "gen": { "height": 690149 } } ], "vout": [ { "amount": 3171571050, "target": { "key": "6e2b91abd28ee0a13435c4746c62bbb2fe0254ff22bef42b42b92e0f0c1e41d3" } } ], "extra": [ 1, 59, 181, 64, 68, 39, 5, 140, 154, 13, 187, 176, 69, 168, 80, 251, 42, 36, 33, 20, 122, 191, 66, 129, 89, 189, 161, 66, 248, 166, 15, 162, 213, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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